Metadata Registry entries
When an image is added to the Multimedia module, metadata is extracted from the file and stored on the appropriate tab:
Tab |
Supports |
---|---|
EXIF | jpeg and tiff formats |
IPTC | jpeg, tiff, pict, ps and psd formats |
XMP | jpeg and tiff formats |
Whenever an image is derived from a master image in
Specify what metadata is copied from a master image to any derived images (resolutions) stored in
When derivatives are generated in
If the Registry entry is not set, no metadata is embedded.
Usage
This Registry entry can be assigned to users, groups and system-wide:
Key | User | Group | Key | System |
---|---|---|---|---|
Key 1 | User
|
Group
|
Key 1 | System
|
Key 2 | user | group | Key 2 | Setting
|
Key 3 | Setting
|
Key 3 | Multimedia
|
|
Key 4 | Multimedia
|
Key 4 | Metadata
|
|
Key 5 | Metadata
|
Key 5 | Embed
|
|
Key 6 | Embed
|
Key 6 | type | |
Key 7 | type | Key 7 | format | |
Key 8 | format | |||
Value | tag;... | Value | tag;... |
User
|
user | Setting
|
Multimedia
|
Metadata
|
Embed
|
type | format | tag;... |
Group
|
group | Setting
|
Multimedia
|
Metadata
|
Embed
|
type | format | tag;... |
System
|
Setting
|
Multimedia
|
Metadata
|
Embed
|
type | format | tag;... |
where:
type |
is the type of metadata to embed. Allowable values are |
format |
defines the image format for which the metadata will be embedded. There are three possible format types:
When determining which Registry entries apply for embedding tags in derivatives, |
tag;... |
The tag list depends on the metadata type selected. The list indicates what properties should be embedded in the derivative. Allowable values are:
|
In this first example the EXIF copyright property (attribute 1:33432
) is to be embedded in all derived images:
Key | Setting |
---|---|
Key 1 | System
|
Key 2 | Setting
|
Key 3 | Multimedia
|
Key 4 | Metadata
|
Key 5 | Embed
|
Key 6 | EXIF
|
Key 7 | Default
|
Value | 1:33432
|
If we want the EXIF copyright text copied into all images except for thumbnails (90 pixel by 90 pixel JPEG), the following two entries would be required:
Key | Setting | Setting |
---|---|---|
Key 1 | System
|
System
|
Key 2 | Setting
|
Setting
|
Key 3 | Multimedia
|
Multimedia
|
Key 4 | Metadata
|
Metadata
|
Key 5 | Embed
|
Embed
|
Key 6 | EXIF
|
EXIF
|
Key 7 | Default
|
90:90:JPEG
|
Value | 1:33432
|
None
|
The next entries will embed the XMP Dublin Core XML in derived TIFF and JPEG images:
Key | Setting | Setting |
---|---|---|
Key 1 | System
|
System
|
Key 2 | Setting
|
Setting
|
Key 3 | Multimedia
|
Multimedia
|
Key 4 | Metadata
|
Metadata
|
Key 5 | Embed
|
Embed
|
Key 6 | XMP
|
XMP
|
Key 7 | TIFF
|
JPEG
|
Value | http://purl.org/dc/elements/1.1/:
|
http://purl.org/dc/elements/1.1/:
|
Note: Notice how only the namespace is specified (it is important to have the trailing colon), indicating that all Dublin Core attributes should be embedded.
The next entry will embed all IPTC Application attributes (Record type 2) except for the MasterDocumentID
and the UniqueDocumentID
in all derivatives:
Key | Setting |
---|---|
Key 1 | System
|
Key 2 | Setting
|
Key 3 | Multimedia
|
Key 4 | Metadata
|
Key 5 | Embed
|
Key 6 | IPTC
|
Key 7 | Default
|
Value | 2:;-2:185;-2:187
|
Finally, the following five entries will ensure that thumbnail images do not store any metadata. For all other derivatives all IPTC metadata is embedded, and for XMP, Dublin Core, IPTC and Rights data is embedded:
Key | Setting | Setting | Setting | Setting |
---|---|---|---|---|
Key 1 | System
|
System
|
System
|
System
|
Key 2 | Setting
|
Setting
|
Setting
|
Setting
|
Key 3 | Multimedia
|
Multimedia
|
Multimedia
|
Multimedia
|
Key 4 | Metadata
|
Metadata
|
Metadata
|
Metadata
|
Key 5 | Embed
|
Embed
|
Embed
|
Embed
|
Key 6 | EXIF
|
IPTC
|
IPTC
|
XMP
|
Key 7 | Default
|
Default
|
90:90:JPEG
|
90:90:JPEG
|
Value | None
|
All
|
None
|
None
|
Key | Setting |
---|---|
Key 1 | System
|
Key 2 | Setting
|
Key 3 | Multimedia
|
Key 4 | Metadata
|
Key 5 | Embed
|
Key 6 | XMP
|
Key 7 | Default
|
Value | http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/; http://ns.adobe.com/xap/1.0/rights/: ;http://purl.org/dc/elements/1.1/:
|
If we assume the settings above and the XMP for the master image is displayed as follows:
then the derivative metadata would look like:
Specify what metadata is extracted from an image and stored in
Usage
This Registry entry can be assigned to users, groups and system-wide:
Key | User | Group | Key | System |
---|---|---|---|---|
Key 1 | User
|
Group
|
Key 1 | System
|
Key 2 | user | group | Key 2 | Setting
|
Key 3 | Setting
|
Key 3 | Multimedia
|
|
Key 4 | Multimedia
|
Key 4 | Metadata
|
|
Key 5 | Metadata
|
Key 5 | Extract
|
|
Key 6 | Extract
|
Key 6 | type | |
Key 7 | type | Key 7 | format | |
Key 8 | format | |||
Value | tag;... | Value | tag;... |
User
|
user | Setting
|
Multimedia
|
Metadata
|
Extract
|
type | column | tag;... |
Group
|
group | Setting
|
Multimedia
|
Metadata
|
Extract
|
type | column | tag;... |
System
|
Setting
|
Multimedia
|
Metadata
|
Extract
|
type | column | tag;... |
where:
type |
is the type of metadata to extract. Allowable values are |
column |
is the name of the column into which the values are to be placed. |
tag;... |
The tag list depends on the metadata type selected. The list indicates what properties should be extracted for inclusion in the Multimedia repository. The tag value is an |
The metadata extracted will only be inserted into the specified column if there is no data already present in the field. It will not overwrite or add to existing data. When extracting metadata that has multiple values into an atomic field,
This entry will extract the IPTC caption attribute (2:120
) and add it to the Title field on the Multimedia tab:
Key | Setting |
---|---|
Key 1 | System
|
Key 2 | Setting
|
Key 3 | Multimedia
|
Key 4 | Metadata
|
Key 5 | Extract
|
Key 6 | IPTC
|
Key 7 | Multitle
|
Value | 2:120
|
The next entry will extract the Dublin Core title attribute and place it in the Title field:
Key | Setting |
---|---|
Key 1 | System
|
Key 2 | Setting
|
Key 3 | Multimedia
|
Key 4 | Metadata
|
Key 5 | Extract
|
Key 6 | XMP
|
Key 7 | Multitle
|
Value | http://purl.org/dc/elements/1.1/:title
|
The next entry will extract the keywords from the IPTC metadata (2:25
) and place them in the Subject/Keywords list on the Details tab:
Key | Setting |
---|---|
Key 1 | System
|
Key 2 | Setting
|
Key 3 | Multimedia
|
Key 4 | Metadata
|
Key 5 | Extract
|
Key 6 | IPTC
|
Key 7 | DetSubject_tab
|
Value | 2:25
|
Finally, the following three entries will try to extract the copyright details from EXIF, IPTC and XMP metadata and place them in the Rights field on the Details tab:
Key | Setting | Setting | Setting |
---|---|---|---|
Key 1 | System
|
System
|
System
|
Key 2 | Setting
|
Setting
|
Setting
|
Key 3 | Multimedia
|
Multimedia
|
Multimedia
|
Key 4 | Metadata
|
Metadata
|
Metadata
|
Key 5 | Extract
|
Extract
|
Extract
|
Key 6 | EXIF
|
IPTC
|
XMP
|
Key 7 | DetRights
|
DetRights
|
DetRights
|
Value | 1:33432
|
2:116
|
http://purl.org/dc/elements/1.1/:rights;http://ns.adobe.com/xap/1.0/rights/:UsageTerms
|
Notice that the last entry looks up both the Dublin Core rights attribute and the XMP Rights Management usage attribute.
Note: When using the Update Resource tool for a selection of records (Multimedia>Update Resource), the metadata extraction Registry entries are not used. If, however, you update the current record (Multimedia>Update Resource>Current Record), the extraction does take place.
Additional details
Information for users about metadata is available here.
Information about each metadata standard supported by